Correct maximum recommended clients per member #1536
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The information currently presented in the docs is outdated, as client tasks are handled by 3 executors instead of 1 now (since 2018). This section also did not mention I/O thread counts which are also relevant when determining client connection limits. This PR updates this section with more details and up-to-date information.
JamesHazelcast
added
Type: Enhancement
backport to 5.3
✅ Deploy Preview for hardcore-allen-f5257d ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
gbarnett-hz
approved these changes
Feb 12, 2025
JamesHazelcast
added a commit
that referenced
this pull request
Feb 13, 2025
The information currently presented in the docs is outdated, as client tasks are handled by 3 executors instead of 1 now (since 2018). This section also did not mention I/O thread counts which are also relevant when determining client connection limits. This PR updates this section with more details and up-to-date information. Backport of: #1536
JamesHazelcast
added a commit
that referenced
this pull request
Feb 20, 2025
The information currently presented in the docs is outdated, as client tasks are handled by 3 executors instead of 1 now (since 2018). This section also did not mention I/O thread counts which are also relevant when determining client connection limits. This PR updates this section with more details and up-to-date information. Backport of: #1536
This was referenced Feb 20, 2025
JamesHazelcast
added a commit
that referenced
this pull request
Feb 20, 2025
Backport of #1544 The information currently presented in the docs is outdated, as client tasks are handled by 3 executors instead of 1 now (since 2018). This section also did not mention I/O thread counts which are also relevant when determining client connection limits. This PR updates this section with more details and up-to-date information. Backport of: #1536 Co-authored-by: James Holgate <[email protected]>
JamesHazelcast
added a commit
that referenced
this pull request
Feb 20, 2025
Backport of #1544 The information currently presented in the docs is outdated, as client tasks are handled by 3 executors instead of 1 now (since 2018). This section also did not mention I/O thread counts which are also relevant when determining client connection limits. This PR updates this section with more details and up-to-date information. Backport of: #1536 --------- Co-authored-by: James Holgate <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The information currently presented in the docs is outdated, as client tasks are handled by 3 executors instead of 1 now (since 2018).
This section also did not mention I/O thread counts which are also relevant when determining client connection limits.
This PR updates this section with more details and up-to-date information.